Leaving as a draft until #577 and Java 11 build are merged in order to uncomment the forRemoval property of the @Deprecated annotations.

I wonder if there's anything we need to do to ensure that when we build the full MicroProfile Javadoc we pick up the API version of this package rather than the SPI one with the deprecation warnings.

Good question, where is it generated and hosted?

Hmm, actually never mind, it doesn't look like the MicroProfile project builds a combined Javadoc anywhere.

We do build one for the Open Liberty docs, but I can poke our docs team to find out how they do it and ask them to not use the SPI jar.